The Web4Ham logfile

All requests from clients are written to the file WEB4HAM.LOG. Only the first line of each request is written to the logfile (with the new HTTP/1.0 protocol hundreds of bytes are sent to the server, sometimes outnumbering the size of a response). You can see everything the client is sending, if you set the LOGALL variable in the INI-file to the value 1. The format of the logfile is identical to the logfile written by the Go4Ham server (which will be soon updated to an asynchronous version). A typical logfile will look like this ("Rigel" is the hostname of my server at home):

19940320,194953,"rigel","Web4Ham/0.14 started"
19940320,195020,"127.0.0.1","GET /maxmor.htm HTTP/1.0"
19940320,195020,"127.0.0.1","HTTP/1.0 200 ok"
19940320,195028,"127.0.0.1","c:\serweb/maxmor.htm 17274 bytes sent"
19940320,195140,"rigel","Web4Ham/0.14 stopped"

Each line consists of 4 items. The first item is the date in the format YYYYMMDD, followed by the time in the format HHMMSS. The third item is the IP-Address of the client and the last item is the first line of the client's request. Start and stop messages from the server contain the name of your host. As this is an alpha version, the logfile might have error messages from the Winsock interface as well, they do not show up on the screen, they are just written to the logfile. The status line of the server is witten to the logfile and if a request has been successful, the retrieved file and its length are logged as well. The status line messages will help you to locate invalid links to documents. The IP address is used to identify the connection (we have to add the socket number if the server is running asynchronous). The logfile is written in SDF format, this format can be handled by many PC database and spreadsheet programs.